Organizing a synchronous communication session according to context

ABSTRACT

Organizing a synchronous communication session can include determining, using a processor of a data processing system, a context responsive to detecting a trigger event. The context specifies a foreground application executing within the data processing system. Candidate participants can be determined from the context. A user interface is displayed separate from the foreground application. The user interface lists the candidate participants. Further, responsive to a user input received within the user interface, an invite to the candidate participants is sent. The invite specifies access information for the synchronous communication session.

BACKGROUND

Within modern work environments, users are required to interact withmany different persons on a daily basis. Often, the persons with whomone must interact are not geographically co-located. As such, users mustrely upon various communication technologies to facilitate interactions.The particular type of communication technology used may be eithersynchronous or non-synchronous. Examples of synchronous communicationsinclude instant messaging, text messaging, online meetings, traditionaltelephony, voice over Internet Protocol (VoIP), video chat, andteleconferencing. Examples of non-synchronous communications includeelectronic mail and discussion boards.

Synchronous communications are technologies that offer real time andpotentially concurrent exchange of data or communications between theparticipants. Non-synchronous communications are not real time andcommunications are not concurrently bi-directional or conversational innature. Synchronous communications provide various advantages overnon-synchronous communications including, for example, increasedefficiency, immediacy, and timeliness to the participant interactions.In order to preserve these benefits, however, a synchronouscommunication session must be organized between the participants withoutplacing an undue burden upon any one participant.

BRIEF SUMMARY

This specification relates to organizing a synchronous communicationsession according to context.

A method includes determining, using a processor of a data processingsystem, a context responsive to detecting a trigger event. The contextspecifies a foreground application executing within the data processingsystem. The method further includes determining candidate participantsfrom the context and displaying a user interface separate from theforeground application, wherein the user interface lists the candidateparticipants. Responsive to a user input received within the userinterface, sending an invite to the candidate participants. The invitespecifies access information for a synchronous communication session.

A system includes a display device and a processor coupled to thedisplay device. The processor is programmed to initiate executableoperations. The executable operations include determining a contextresponsive to detecting a trigger event. The context specifies aforeground application executing within a data processing systemincluding the processor. The executable operations also includedetermining candidate participants from the context and displaying uponthe display device a user interface separate from the foregroundapplication, wherein the user interface lists the candidateparticipants. Responsive to a user input received within the userinterface, an invite is sent to the candidate participants. The invitespecifies access information for a synchronous communication session.

A computer program product includes a computer readable storage mediumhaving program code stored thereon. The program code is executable by aprocessor to perform a method. The method includes determining, usingthe processor of a data processing system, a context responsive todetecting a trigger event. The context specifies a foregroundapplication executing within the data processing system. The method alsoincludes determining, using the processor, candidate participants fromthe context and displaying, using the processor, a user interfaceseparate from the foreground application upon a display device. The userinterface lists the candidate participants. The method further includes,responsive to a user input received within the user interface, sending,using the processor, an invite to the candidate participants, whereinthe invite specifies access information for a synchronous communicationsession.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an exemplary network system.

FIG. 2 is a block diagram illustrating an exemplary architecture for adata processing system.

FIG. 3 is a block diagram illustrating an exemplary executionenvironment including a context agent.

FIG. 4 is a block diagram illustrating an exemplary user interface forthe context agent of FIG. 3.

FIG. 5 is a flow chart illustrating an exemplary method of organizing asynchronous communication session.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer-readablemedium(s) having computer-readable program code embodied, e.g., stored,thereon.

Any combination of one or more computer-readable medium(s) may beutilized. The computer-readable medium may be a computer-readable signalmedium or a computer-readable storage medium. A computer-readablestorage medium may be, for example, but is not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, or device, or any suitable combinationof the foregoing. More specific examples (a non-exhaustive list) of thecomputer-readable storage medium would include the following: anelectrical connection having one or more wires, a portable computerdiskette, a hard disk drive (HDD), a solid state drive (SSD), a randomaccess memory (RAM), a read-only memory (ROM), an erasable programmableread-only memory (EPROM or Flash memory), an optical fiber, a portablecompact disc read-only memory (CD-ROM), a digital versatile disc (DVD),an optical storage device, a magnetic storage device, or any suitablecombination of the foregoing. As defined herein, the term“computer-readable storage medium” means a tangible storage medium thatcontains or stores program code for use by or in connection with aninstruction execution system, apparatus, or device.

A computer-readable signal medium may include a propagated data signalwith computer-readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer-readable signal medium may be any computer-readable medium thatis not a computer-readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer-readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber, cable, RF, etc., or any suitable combination ofthe foregoing. Computer program code for carrying out operations foraspects of the present invention may be written in any combination ofone or more programming languages, including an object orientedprogramming language such as Java™, Smalltalk, C++ or the like andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The program codemay execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer, or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (LAN) or a wide area network (WAN), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer, other programmable data processing apparatus,or other devices create means for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable medium that can direct a computer, other programmabledata processing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

For purposes of simplicity and clarity of illustration, elements shownin the figures have not necessarily been drawn to scale. For example,the dimensions of some of the elements may be exaggerated relative toother elements for clarity. Further, where considered appropriate,reference numbers are repeated among the figures to indicatecorresponding, analogous, or like features.

This specification relates to synchronous communications and, moreparticularly, to organizing a synchronous communication sessionaccording to context. In accordance with the inventive arrangementsdisclosed within this specification, the context in which a user isworking can be determined. In one aspect, the context is determinedresponsive to a trigger event. In general, detection of the triggerevent serves as an indication that the user wishes to communicate withone or more other users having a relationship to activities beingperformed by the user as reflected in the context.

From the context, one or more candidate participants for a synchronouscommunication session are determined. Further, a presence, or presenceinformation, for each candidate participant may be determined.Accordingly, a user can be presented with a user interface (UI) thatincludes a list of the candidate participants determined from thecontext in which the user is working. Presence for the candidateparticipants can be presented through the UI. Using the UI and theinformation presented therein, the user may select a particular type ofsynchronous communication channel over which to establish thesynchronous communication session. Responsive to one or more user inputsfrom the user, a synchronous communication session may be setup and/orestablished. Further, invites to join the synchronous communicationsession can be sent to the candidate participants or selected candidateparticipants as the case may be.

As used herein, a “synchronous communication channel” refers to acommunication technology that offers real time and concurrent exchangeof data or communications between the participants. Examples ofsynchronous communication channels include, but are not limited to,instant messaging, text messaging, online meetings, traditionaltelephony, voice over Internet Protocol (VoIP), video chat, onlinescreen sharing, and teleconferencing. A “synchronous communicationsession” refers to a semi-permanent interactive information exchangeconducted over a selected synchronous communication channel. The phrase“real time” means a level of processing responsiveness that a user orsystem senses as sufficiently immediate for a particular process ordetermination to be made, or that enables the processor to keep up withsome external process.

FIG. 1 is a block diagram illustrating an exemplary network system 100.Network system 100 includes a plurality of clients 105, 110, 115, and120. Network system 100 further can include a synchronous communicationsystem 125. Each of client systems 105, 110, 115, and 120 andsynchronous communication system 125 can be implemented as a dataprocessing system. Synchronous communication system 125 may beimplemented as a plurality of inter-connected data processing systems orservers.

Synchronous communication system 125 can communicate with, and support,synchronous communications between clients 105, 110, 115, and 120 overnetwork 130. For example, synchronous communication system 125 canimplement or host a synchronous communication session that can be joinedby one or more or all of clients 105, 110, 115, and/or 120.

Network 130 is the medium used to provide communications links betweenvarious devices illustrated in network system 100. Network 130 mayinclude connections, such as wire, wireless communication links, orfiber optic cables. Network 130 can be implemented as, or include, anyof a variety of different communication technologies such as a WAN, aLAN, a wireless network, a mobile network, a Virtual Private Network(VPN), the Internet, the Public Switched Telephone Network (PSTN), orthe like.

In the example pictured in FIG. 1, each of clients 105, 110, 115, and120 can be operated by a user. The term “user” means a human being thatis operating and/or accessing a particular client. Each of clients105-120 can be said to be “associated” with the particular user that isoperating the client. Within this specification, a reference to aparticular user may also refer to the client associated with, or usedby, that user. Similarly, reference to a particular client may alsorefer to the user associated with that client. For example, reference toclient 105 may also refer to the user of client 105. For purposes ofdiscussion, user 105 is the user of client 105. Similarly, user 110 isthe user of client 110, etc.

As pictured, client 105 is communicatively linked through a wirelesscommunication link 135 to a peripheral device 140. In one aspect,wireless communication link 135 can be a near field wirelesscommunication link such as, for example, one that is compliant withBluetooth® Core Version 4.0, an earlier version of the specification, anas of yet unreleased implementation of the specification, an 802.11 typewireless connection, or the like. While illustrated as wirelesscommunication link 135, it should be appreciated that peripheral device140 may be communicatively linked to client 105 by way of a physicalconnection such as a cable, e.g., universal serial bus (USB), firewire,or the like.

In one aspect, peripheral device 140 can include one or more transduciveelements such as a speaker and/or a microphone. Accordingly, a user ofclient 105 may listen and speak through peripheral device 140 whenparticipating in a synchronous communication session. In one example,peripheral device 140 is implemented as a wearable peripheral device. Awearable peripheral device is one that the user must put on or “don.”Such a peripheral device, for example, is worn on a part of the user'sbody, attached to the user's clothing, or the like. Examples of wearableperipheral devices can include earpieces and/or headsets. Anotherexample of a wearable peripheral device includes a wrist worncombination of one or more of the aforementioned transducive elements.Still, peripheral device 140 can be one that is intended to be held asopposed to one that is wearable.

In another aspect, peripheral device 140 can include a motion sensor.One example of a motion sensor is an accelerometer. Inclusion of amotion sensor allows peripheral device 140 to generate a signal or otherindication responsive to being moved or responsive to detecting aparticular type of motion or movement. For example, peripheral device140 can be configured to send a signal recognized as a trigger event byclient 105 responsive to a user putting on or donning, or picking upperipheral device 140. The trigger event is sent from peripheral device140 to client 105.

Consider the case where user 105 is working using client 105.Accordingly, client 105 includes an execution environment in which oneor more different applications are executed. While working, user 105puts on a headset, e.g., peripheral device 140. Movement of peripheraldevice 140 and, more particularly, the act of user 105 donningperipheral device 140, is detected through the use of the motion sensorcontained therein. Accordingly, peripheral device 140 sends a triggerevent to client 105 responsive to the detected movement.

While the trigger event may be a physical movement of an object that isphysically separate and independent from client 105, it should beappreciated that the trigger event can be any of a variety of differentinputs from user 105. For example, other trigger events can include, butare not limited to, user input selecting one or more keys, e.g., a keycombination, a user spoken utterance, or the like.

Responsive to the trigger event, client 105 determines which of theapplications executing therein is currently active or has “focus.” Theapplication that is “in focus” is said to be in the foreground and maybe referred to as the “foreground application.” In this example,application 145 is the foreground application when the trigger event isdetected. Client 105 determines a context specifying information forapplication 145. From the determined context, client 105 furtherdetermines one or more candidate participants for a synchronouscommunication session that may be established. In one aspect, client 105can determine the availability of each such candidate participant andpresent a UI 150 to user 105 listing the candidate participants andproviding a means by which user 105 can initiate the synchronouscommunication session with each such candidate participant.

UI 150 can be independent or separate from application 145. Asillustrated in FIG. 1, UI 150 is displayed as a window that is separateand distinct from the window corresponding to application 145. From UI150, user 105 can initiate a synchronous communication session with oneor more of the listed candidate participants. For example, user 105 canselect a control within UI 150 that causes a synchronous communicationsession to be setup or established within and/or by synchronouscommunication system 125. Further, user 105 can select a control withinUI 150, e.g., the same control and/or a different control, therebycausing an invite 155 to be sent to users 110, 115, and 120. In thisexample, users 110, 115, and 120, corresponding to clients 110, 115, and120, respectively, are candidate participants for the synchronouscommunication session since users 110, 115, and 120 were determined fromthe aforementioned context.

Presentation of candidate participants within UI 150 streamlines theprocess of organizing a synchronous communication session. The contextthat is derived is presumed to be instructive of the particular issuethat user 105 is attempting to resolve. Further, the context is presumedto be instructive of the particular candidate participants, e.g., users110, 115, and/or 120, who may be needed for participation within thesynchronous communication session in order for user 105 to resolve theissue.

Typically, while working in an application such as a browser applicationand/or a productivity application, the names of candidate participantsor other actionable elements that allow candidate participants to bedetermined are linked or listed within the particular digital asset thatis open within the application. Thus, in order to resolve an issue whileworking, it is often the case that user 105 would like to start asynchronous communication session with one or more candidateparticipants that may be discernible from the context within client 105that exists when a trigger event is detected. The context of client 105includes, for example, the foreground application. The context furthercan include any digital asset open therein or currently being displayedby the foreground application. The embodiments described herein providefor the seamless organization and/or initiation of a synchronouscommunication session based upon such context. Accordingly, for purposesof illustration, consider the following exemplary situations where user105 may find it desirable to initiate a synchronous communicationsession with candidate participants determined from context of client105.

In one example, while reading an electronic mail, user 105 decides thatmore immediate communication with the sender and/or one or more otherrecipients of the electronic mail is required. Responsive to user 105placing an earpiece, e.g., peripheral device 140, on his or her ear, UI150 is displayed presenting a list of candidate participants. In thisexample, each person that received the electronic mail is a candidateparticipant. UI 150 further can include one or more controls that allowuser 105 to send invite 155 to each listed candidate participantinviting that candidate participant to participate in a conference callhosted by synchronous communication system 125. As noted, presence foreach candidate participant, e.g., online presence information which caninclude availability as determined by a calendar or other schedule, alsocan be displayed if available.

In another example, while browsing a project status Web page rendered ina browser application, user 105 decides that an online meeting is neededfor one or more of the persons named on the Web page currently beingviewed. Such persons are considered candidate participants in thisexample. Responsive to user 105 selecting a hotkey, UI 150 is displayed.UI 150 includes a list of the candidate participants that were listed onthe Web page. As noted, presence may be displayed for each candidateparticipants if available. Through UI 150, the online meeting isestablished, or activated within synchronous communication system 125.Further, responsive to user inputs provided to UI 150, selected ones ofthe candidate participants listed in UI 150 receive invite 155 to theonline meeting. It should be appreciated that the trigger event in thisexample also may be the donning of peripheral device 140.

Invite 155 can be sent via instant message, electronic mail, shortmessage service (SMS), or the like. Alternatively, invite 155 can besent to selected candidate participants via a phone call. For example,an interactive voice response system can place a call to each selectedcandidate participant and provide information needed by the candidateparticipant to join the synchronous communication session. Thus, invite155 can be sent via a different communication channel than is used forthe synchronous communication session. Further, the communicationchannel over which invite 155 is sent need not be synchronous, e.g.,where electronic mail is used.

In still another example, while operating a productivity applicationsuch as a word processing application, user 105 determines that a reviewof the document currently being edited or viewed is required. Responsiveto user 105 donning an earpiece, UI 150 is presented. UI 150, forexample, can display a thumbnail image of the current document andsummary information. In one aspect, the candidate participantsassociated with the document are listed in UI 150. In another aspect,using a voice-driven lookup service, user 105 creates a list of nameswithin UI 150. In either case, user 105 can invoke a command via UI 150that causes invite 155 to be sent to the selected candidateparticipants. Invite 155 can invite the selected candidate participantsto a conference call and to an online sharing session where the documentbeing viewed by user 105 is displayed for purposes of discussion. Theconference call and the online sharing session can be hosted orfacilitated by synchronous communication system 125.

In another aspect, the clients that receive invite 155 as described inthe examples above may also store prior contexts that can be retrieved.For example, responsive to user 110 and client 110 receiving invite 155from user 105, one or more contexts may be retrieved and presented byclient 110 to user 110. Each context that is retrieved and presented byway of client 110 can be one that existed concurrently or during a priorcommunication session between user 110 and user 105. The list ofcontexts presented can specify information such as a particular Webpage, document, or the like that was viewed and/or the subject of aprior communication whether a synchronous communication session or anon-synchronous communication session between users 105 and 110. Assuch, the candidate participants that receive invite 155 may retrievelikely contexts and/or reasons for the particular invite that isreceived. The retrieved contexts for user 110, however, can be filteredor limited to only those involving user 105, e.g., communication withuser 105.

FIG. 2 is a block diagram illustrating an exemplary architecture for adata processing system (system) 200. The architecture pictured in FIG. 2can be used to implement any of clients 105, 110, 115, and/or 120 ofFIG. 1. Further, the architecture pictured in FIG. 2 can be used toimplement one or more servers of synchronous communication system 125 ofFIG. 1.

As pictured, system 200 can include at least one processor 205, e.g., acentral processing unit, coupled to memory elements 210 through a systembus 215 or other suitable circuitry. System 200 can store program codewithin memory elements 210. As illustrated, system 200 stores a contextagent 250 within memory elements 210. Processor 205 executes the programcode accessed from memory elements 210 via system bus 215 or the othersuitable circuitry.

In one aspect, system 200 is implemented as a computer or otherprogrammable data processing apparatus that is suitable for storingand/or executing program code. It should be appreciated, however, thatsystem 200 can be implemented in the form of any system including aprocessor and memory that is capable of performing and/or initiating thefunctions and/or operations described within this specification.

Memory elements 210 include one or more physical memory devices such as,for example, local memory and one or more bulk storage devices. Localmemory refers to RAM or other non-persistent memory device(s) generallyused during actual execution of the program code. A bulk storage devicecan be implemented as an HDD, SSD, or other persistent data storagedevice. System 200 also can include one or more cache memories (notshown) that provide temporary storage of at least some program code inorder to reduce the number of times program code must be retrieved froma bulk storage device and/or RAM during execution.

Input/output (I/O) devices such as a keyboard 230, a display device 235,and a pointing device 240 optionally can be coupled to system 200. TheI/O devices can be coupled to system 200 either directly or throughintervening I/O controllers. One or more network adapters 245 also canbe coupled to system 200 to enable system 200 to become coupled to othersystems, computer systems, remote printers, and/or remote storagedevices through intervening private or public networks. Modems, cablemodems, wireless transceivers, and Ethernet cards are examples ofdifferent types of network adapters 245 that can be used with system200. Peripheral device 140 of FIG. 1, for example, whether wired orwireless, can communicate with system 200 via network adapter 245.

System 200 can be implemented in any of a variety of different formfactors. As a server, for example, system 200 may or may not include I/Odevices such as keyboard 230, display 235, and/or pointing device 240.As a client, system 200 can be implemented as a personal computer, aportable computer, e.g., a laptop, a tablet, a mobile communicationdevice, or the like. For example, system 200 can include I/O devicessuch as keyboard 230, display device 235, and pointing device 240 in anyof a variety of different configurations, e.g., as an integrated displaydevice in the form of a flat panel display or touchscreen that replaceskeyboard 230 and/or pointing device 240, etc.

As noted, memory elements 210 can store program code that includescontext agent 250 and an operating system (not shown). In the case of aclient, context agent 250, when executed, causes system 200 to performthe various operations described within this specification. It should beappreciated that context agent 250, including any parameters and/orattributes utilized by context agent 250, i.e., a context, digitalassets, etc., are functional data structures that impart functionalitywhen employed as part of system 200.

FIG. 3 is a block diagram illustrating an exemplary executionenvironment 300 including a context agent. Execution environment 300 isrepresentative of the execution environment implemented, or existing,within client 105 of FIG. 1. As shown, execution environment 300includes a context agent 250, a browser application 305, a productivityapplication 310, a client synchronous communication (CSC) application315, and address data 320. Peripheral device 140, which is a physicaldevice not part of execution environment 300, also is shown for purposesof illustration and description.

In one aspect, context agent 250 is implemented as a continuallyresident program and is configured to perform a variety of differentfunctions. Context agent 250 monitors activity within the client todetermine a current context for the client. As part of the monitoringactivity, context agent 250 continually tracks and/or determines theparticular application that is executing within the client as theforeground application. Additional details such as the digital assetthat is open or displayed within the foreground application also can bedetermined as part of the context. A digital asset refers to a file thatmay be opened by the foreground application. Still, other detailsrelating to operation of the client can be determined as part of thecontext.

The way in which context agent 250 determines context can vary. In oneaspect, context agent 250 communicates with the foreground applicationby way of a plug-in. As an illustrative example, context agent 250communicates with browser application 305 through plug-in 325. Plug-in325 executes and interacts with browser application 305 using thestandard application programming interfaces (APIs) provided by browserapplication 305.

In the case of browser application 305, the digital asset may be a Webpage. When a user opens and/or views a Web page within browserapplication 305, for example, browser application 305 is the foregroundapplication. The phrase “Web page,” as used herein, can refer to any ofa variety of markup-language documents and/or other documents that canbe displayed or rendered by browser application 305. Accordingly,context agent 250 is aware that browser application 305 is theforeground application and further is aware of the particular digitalasset that is being viewed or rendered therein. In this regard, contextagent 250 has access to the digital asset, e.g., the Web page, renderedwithin browser application 305 through plug-in 325. The digital assetmay be parsed or otherwise evaluated by context agent 250.

Context agent 250 also can communicate with an application by way of anadapter. For example, context agent 250 communicates with productivityapplication 310 through adapter 330. Adapter 330 is an interfacecomponent that reads context from productivity application 310 throughthe applicable APIs provided by productivity application 310. Adapter330 communicates context for productivity application 310 to contextagent 250. When a user opens and/or views a digital asset such as anelectronic mail, a word processing document, a spread sheet, apresentation, a drawing, etc., through productivity application 310,context agent 250 is aware that productivity application 310 is theforeground application. Further, the digital asset opened withinproductivity application 310 is made available to context agent 250 byadapter 330.

In still another aspect, an application can communicate with contextagent 250 through a service layer 335 thereby supporting customcontexts. Browser application 305 and productivity application 310 areexamples where integration with context agent 250 is achieved after thefact. In those cases, integration is achieved through the use of thevarious extensibility services provided by each respective application.Custom context 340, however, illustrates an example in which theapplication is built with specific knowledge of context agent 250. Assuch, custom context 340 utilizes APIs of context agent 250 as accessedthrough service layer 335 to communicate a context.

CSC application 315 represents any of a variety of synchronouscommunication applications that may be executed within a client. Forexample, CSC application 315 can establish synchronous communicationsessions over any of a variety of available synchronous communicationchannels. As noted, examples of synchronous communication channelsinclude, but are not limited to, instant messaging, text messaging,VOIP, conventional telephone, online web meetings including contentsharing, teleconferences, or the like. In one aspect, CSC application315 can be implemented as a stand-alone application, e.g., aninteractive desktop application, having a dedicated UI. In anotheraspect, however, CSC application 315 can be implemented as a residentservice capable of performing the aforementioned operations undercontrol of context agent 250 without providing a UI. Further examples ofCSC application 315 include, but are not limited to, an XMPP client, amultiprotocol client, a federated client, or the like.

As pictured in FIG. 3, context agent 250 can communicate with peripheraldevice 140. As such, any trigger events generated and sent fromperipheral device 140 to the client are received and processed bycontext agent 250. As noted, context agent 250 can perform variousoperations responsive to a received trigger event from peripheral device140. Context agent 250 can establish or initiate a synchronouscommunication session based upon the context in existence when thetrigger event is received from peripheral device 140.

Address data 320 is a data structure stored within a computer-readablestorage medium within the client that stores identifying information forcontacts. For example, address data 320 includes one or more contactentries. Each entry can include a name and one or more correlated orassociated addresses for the name. Each address may be associated with,or used for, establishing a communication session with the contact. Forexample, a given entry may specify a name, an instant messaging address,an electronic mail address, an address for a telephone call (e.g., aphone number), or the like. Address data 320 further supports queryingand lookup operations according to any of a variety of different searchattributes. For example, address date 320 can be queried using a name sothat one or more addresses can be retrieved. In another example, anaddress can be used to retrieve a name and/or additional addresses for auser. Address data 320 may be integrated within CSC application 315, butthis need not be the case. The various embodiments disclosed within thisspecification effectively integrate synchronous communications with awide range of applications without the need for modifying thoseapplications.

In conventional approaches, to the extent that synchronouscommunications are made accessible, such is the case through a real timecommunications API that must be used and incorporated into eachapplication by the developer. For example, in the case of a Web page thedeveloper or owner of the Web page must modify the Web page (or otherapplication as the case may be) to utilize the real time API.Incorporation of the real time API, however, introduces into theapplication an unwelcome level of complexity and a dependency uponforeign program code in reference to the API being developed by a thirdparty. Further, integration of the API must be performed for eachapplication for which synchronous communications are to be madeaccessible.

Typically, while working in an application such as browser application305 and/or productivity application 310, the names or other actionableelements that allow the names of contacts to be determined are linked orlisted within the particular digital asset that is open within theforeground application. Thus, when attempting to resolve an issue whileworking, it is often the case that the user would like to quickly starta synchronous communication session with one or more of the personsnamed in the foreground application without having to leave thatcontext, e.g., application, to do so. The embodiments described hereinaccomplish the seamless organization and/or initiation of suchsynchronous communication sessions and, in addition, facilitatemulti-party versions of synchronous communication sessions.

FIG. 4 is a block diagram illustrating an exemplary UI for the contextagent of FIG. 3. FIG. 4 illustrates a UI 405 for browser application305. Further, UI 150 of context agent 250 is presented. In the exampleshown, a trigger event has been detected by context agent 250.Accordingly, a context has been determined from browser application 305.

As shown, the digital asset opened within browser application 305 listsa plurality of contacts shown as “contact 1,” “contact 2,” “contact 3,”and “contact 4.” Context agent 250 processes the received digital assetand identifies contacts 1, 2, 3, and 4 from the digital asset. Inanother example, address data 320 can be used to determine contacts 1,2, 3, and 4 from the detected phrase “Development Group A.” For example,address data 320 can include an organizational chart indicating thatcontacts 1, 2, 3, and 4 are members of Development Group A. Accordingly,even if the digital asset opened within browser application 305 did notexplicitly list contacts 1, 2, 3, and 4, context agent 250 may determinecontacts 1, 2, 3, and 4 from address data 320 from looking up“Development Group A”. From the context, a list of candidateparticipants including “contact 1,” “contact 2,” “contact 3,” and“contact 4” is presented within UI 150.

Thus, responsive to a trigger event, a context is determined by contextagent 250. The context specifies that browser application 305 is theforeground or in focus application. The context further specifies theparticular Web page rendered within browser application 305. As noted,whether by custom context, plug-in, or adapter, the actual Web page isavailable to context agent 250. Accordingly, context agent 250 can parsethe Web page to identify any names for any contacts listed therein.Further, addresses for each contact can be determined by context agent250 from address data 320.

In the example shown in FIG. 4, presence information for each contact isshown thereby indicating the particular communication channel(s) overwhich each candidate participant is available. The user that caused thedetected trigger event, e.g., user 105 of client 105, may select whichof the listed candidate participants are to receive an invite for asynchronous communication session. In the example shown in FIG. 4, theuser selects contact by checking the appropriate checkbox control.Further, the user is able to select the particular type of synchronouscommunication session that is to be established using control 410.

While the user is provided with the ability to select a particular typeof synchronous communication session that is to be established, inanother aspect, the choice of the particular type of synchronouscommunication session to be established is made automatically by contextagent 250. For example, context agent 250 can determine or identify eachcandidate participant in the list presented in UI 150 that is selectedby the user. Context agent 250 then can select a particular type ofsynchronous communication session for which each selected candidateparticipant is available per the presence information. In cases wherethe selected candidate participants may participate in more than onedifferent type of synchronous communication session, context agent 250may select a particular type of synchronous communication sessionaccording to a prioritized list that may be specified by the user.

Once the user has selected candidate participants from UI 150 and a typeof synchronous communication session has been determined, the user mayselect control 415. Responsive to a user selection of control 415,context agent 250 communicates with synchronous communication system 125to set up and/or establish a synchronous communication session of thetype selected if applicable. In another example, context agent caninstruct CSC application 315 to setup and/or establish a synchronouscommunication session of the type selected if applicable.

Further, context agent 250 sends an invite to each selected contact orinstructs CSC application 315 to send such an invite. The invite that issent includes any information necessary for the recipient of the inviteto join the synchronous communication session established withinsynchronous communication system 125. For example, the invite caninclude hyperlinks, teleconference numbers, passcodes, or the like asmay be required depending on the type of synchronous communicationsession that is established.

It should be appreciated that the particular implementation of UI 150may vary and is not intended to be limited by the example provided.Those skilled in the art will recognize that the information containedwithin UI 150 can be presented using any of a variety of differentvisualization techniques and that the controls shown may vary dependingupon preference.

FIG. 5 is a flow chart illustrating an exemplary method 500 oforganizing a synchronous communication session. Method 500 can beperformed by a client executing a context agent as described within thisspecification. For example, method 500 may be performed by client 105.

In block 505, a trigger event is generated. In one aspect, the triggerevent is a user input specifying one or more predetermined keys, aselection of a graphical UI element or control, a particular user spokenutterance interpreted as a trigger event, or the like. In anotheraspect, the trigger event is the act of a user putting on a peripheraldevice and/or picking up a peripheral device as may be detected using amotion detector within the peripheral device.

In block 510, the client and, more particularly, the context agent,receives the trigger event. In block 515, responsive to the triggerevent, the client determines the foreground application. For example,the context agent executing within the client may determine that aproductivity application or a browser is the foregoing application.

In block 520, a communication channel is established between the contextagent and the foreground application. Communication between the contextagent and the foreground application can be facilitated by a customprogramming solution, an adapter, and/or a plug-in as previouslydescribed. In one aspect, for example, the context agent establishes aninter-process communication (IPC) channel with the foregroundapplication. For example, the context agent can open an IPC channel withthe plug-in of the browser application. The IPC channel can beimplemented as a TCP/IP socket, a named pipe, shared memory, or anotherstandard operating system capability.

In block 525, the context agent receives a digital asset that is openwithin the foreground application. The digital asset is received by thecontext agent over the established communication channel. For example,when the foreground application is a browser application, the digitalasset can be a Web page. When the foreground application is aproductivity application, the digital asset can be a word processingdocument, a spreadsheet, a presentation, an electronic mail, a drawing,or the like. In any case, the digital asset can include content andmetadata such as the author, owner, responsible party or group, etc.

The context agent can receive the digital asset in any of a variety ofdifferent formats. In one example, the context agent can receive thedigital asset in its native form or file format. Other exemplary formsin which the digital asset can be provided and received by the contextagent can include, but are not limited to, document object model (DOM)form, raw text, or the like. In cases where the digital asset isreceived as raw text, the context agent may convert or parse the rawtext of the digital asset to create a DOM representation of the digitalasset.

Accordingly, the context determined by the context agent includes theforeground application. The context determined by the context agentfurther may include the digital asset that is open within the foregroundapplication. The context determined by the context agent, however, caninclude additional information. As another example, the context agentcan determined, as part of the context, whether the digital asset wasobtained from an intranet site or another site that is accessible by thepublic, e.g., not restricted or limited to particular segments ormembers of the public.

In block 530, the context agent determines one or more candidateparticipants from the context. In one aspect, the context agentanalyzes, e.g., parses, the received digital asset to identify names,addresses, and/or other actionable items contained therein. For example,the DOM of the digital asset can be evaluated whether the digital assetis a Web page, a word processing document, a spreadsheet, or any of theother examples already discussed to identify tags, names, addresses, orother actionable items such as particular attributes, etc., containedtherein. As noted, candidate participants can be determined from theactual content of the digital asset as well as from the metadata of thedigital asset. The content of the digital asset includes the portions ofthe digital asset that are viewable within the foreground application.

It should be appreciated that the context agent can perform any of avariety of different searches against the address data using anyactionable items of information obtained from the context to determinecandidate participants. Further, the particular type(s) of searchesconducted can vary according to the type of the foreground applicationand/or the particular type of digital asset that is being evaluated.Exemplary searches that can be conducted by the context agent caninclude scanning for electronic mail addresses, scanning for tagsassociated with names and/or addresses, scanning for names, etc.Further, the manner in which the search is conducted can vary. In somecases, for example, the search can be conducted against a cached versionof the digital asset. In other cases, the search can be limited tolocating actionable data items that are visible by an end user when thedigital asset is rendered within the foreground application.

As previously noted, having determined one or more actionable dataitems, address data can be accessed by the context agent. The addressdata can be used to determine addresses for located names, determinenames for located addresses, determine alternate addresses for locatednames and/or addresses, etc. Since the address data may include anorganizational chart, hierarchical data for an organization, role data,etc., the context agent also may determine one or more candidateparticipants from an actionable data item such as a group name or rolefound from the context.

In block 535, the context agent can determine a presence for eachcandidate participant determined in block 530. For example, the contextagent can determine presence for candidate participants from the CSCapplication, or more than one such application, also executing withinthe client. In another aspect, the presence of a candidate participantincludes availability of the candidate participant as may be determinedfrom a calendar for the candidate participant. In any case, anydetermined addresses and/or names for each candidate participant can besent to the CSC application(s) and/or calendaring system as a requestfor presence data for the addresses and/or names as the case may be.Presence data is then provided back to the context agent in response tothe request(s).

In block 540, the context agent displays a UI. The UI that is displayedcan be separate from the foreground application. More particularly, theUI can be a separate window from the window containing the foregroundapplication. The UI can include a list of the candidate participantsdetermined from the aforementioned evaluation of the context. Within theUI, the context agent further can present the presence for each listedcandidate participant. Notwithstanding the prior described UI example ofFIG. 4, further examples of how presence may be specified within the UIfor a candidate participant include, but are not limited to,“available,” “in a meeting,” “Offline,” or the like.

In block 545, the context agent receives one or more user inputs throughthe displayed UI. The received user input(s) can specify one or moreimplementation parameters for the synchronous communication session tobe established. For example, the user input(s) can select one or morecandidate participants that are to receive an invite and participate inthe synchronous communication session. The user input(s) further canselect a particular synchronous communication channel over which thesynchronous communication session is to be conducted. In anotherexample, the user input(s) can specify a communication channel overwhich the invite to the synchronous communication session are to besent.

As discussed, however, the context agent can automatically select theparticular synchronous communication channel to be used for thesynchronous communication session. Regardless of whether the user or thecontext agent selects the synchronous communication channel, the optionscan be limited to those available within the CSC application(s) that areexecuting, may be executing, and accessible by the context agent withinthe client.

In block 550, a synchronous communication session is established orsetup. For example, the context agent can communicate with the CSCapplication and instruct the CSC application to establish a synchronouscommunication session with the relevant synchronous communicationsystem. For example, the context agent can instruct the CSC applicationto arrange an online meeting, arrange a teleconference having a call innumber and passcodes, arrange an online sharing session, etc. In somecases, the setup for a synchronous communication session may not berequired. For example, a user may have a dedicated passcode and accessto a teleconference number. Accordingly, block 550 can be skipped as thesynchronous communication session remains available to the user andparticipants. Such functionality need not be setup in advance.

In block 555, an invite is sent to each contact selected from the listof candidate participants presented in the UI. In one aspect, thecontext agent instructs the CSC application to send an invite to eachselected candidate participant. The invite can provide instructions suchas hyperlinks, telephone numbers, passcodes, and/or the like for thereceiving candidate participant to join the synchronous communicationsession. Once the invite is received, each recipient contact is able tofollow the instructions provided and access the synchronouscommunication session. Further, the context agent of the organizing usercan invoke the appropriate interface of the CSC application to start thespecified synchronous communication session. Each client of a candidateparticipant may also have a context agent executing therein that caninvoke or start the necessary CSC application(s). The context agent mayor may not remain minimized during the described operations.

In block 560, the client(s) that receive the invite optionally performone or more operations in response to receipt and/or acceptance of theinvite. For example, responsive to receipt and/or acceptance of aninvite as described, the client of the candidate participant(s) cansearch stored contexts for interactions between the candidateparticipant and the sender of the invite. Any stored context(s) thatmatch one or more aspects of the current context can be recalled. Forexample, a prior stored context between the candidate participant andthe sender of the invite can be said to match the current context andrecalled. In another example, a matching context can be a prior storedcontext between the candidate participant and the sender of the invitein which the digital asset is also the same. As such, any aspects of therecalled context, e.g., the digital asset(s) previously discussed orshared, also can be recalled and made available to the candidateparticipant.

In accordance with the inventive arrangements disclosed herein, a useris able to initiate a synchronous communication session without leavingthe user's current context. Further, the candidate participants of thesynchronous communication session to be established are determineddirectly from the user's current context. By automatically monitoringthe user's current context and determining the participants from thecurrent context, the likelihood of including participants necessary ordesirable for resolving an issue experienced by the user is increased.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “includes,”“including,” “comprises,” and/or “comprising,” when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment disclosed within thisspecification. Thus, appearances of the phrases “in one embodiment,” “inan embodiment,” and similar language throughout this specification may,but do not necessarily, all refer to the same embodiment.

The term “plurality,” as used herein, is defined as two or more thantwo. The term “another,” as used herein, is defined as at least a secondor more. The term “coupled,” as used herein, is defined as connected,whether directly without any intervening elements or indirectly with oneor more intervening elements, unless otherwise indicated. Two elementsalso can be coupled mechanically, electrically, or communicativelylinked through a communication channel, pathway, network, or system. Theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill also be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms, as these terms are only used to distinguishone element from another unless stated otherwise or the contextindicates otherwise.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the embodiments disclosed within this specification havebeen presented for purposes of illustration and description, but are notintended to be exhaustive or limited to the form disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of theembodiments of the invention. The embodiments were chosen and describedin order to best explain the principles of the invention and thepractical application, and to enable others of ordinary skill in the artto understand the inventive arrangements for various embodiments withvarious modifications as are suited to the particular use contemplated.

1-16. (canceled)
 17. A computer hardware system associated with a user,comprising: a hardware processor configured to initiate the followingexecutable operations: detecting the user donning a wearable peripheraldevice communicatively linked with the computer hardware system;retrieving, based upon the detecting, an email currently being displayedby an email application executing within the computer hardware system;displaying, within a user interface separate from the email application,a list of candidate participants identified from the email; and sending,to at least one of the candidate participants selected from within theuser interface, an invite for a synchronous communication session. 18.The system of claim 17, wherein the retrieving is performed by a contextagent executing within the computer hardware system and separate fromthe email application.
 19. The system of claim 18, wherein the contextagent is configured to communicate with the email application andreceive the email.
 20. The system of claim 18, wherein the context agentis configured to identify an availability of each of the candidateparticipants.
 21. The system of claim 20, wherein an availability of aparticular candidate participant is displayed within the user interface.22. The system of claim 20, wherein the context agent is configured toselect a particular type of synchronous communication session based uponavailabilities of the candidate participants.
 23. The system of claim17, wherein the detecting is based upon a movement of the wearableperipheral device.
 24. The system of claim 17, wherein the invite issent only to each candidate participant selected within the userinterface.
 25. The system of claim 17, wherein the user interfacepresents a plurality of different synchronous communication channels,and the synchronous communication session is conducted over asynchronous communication channel selected from the plurality ofdifferent synchronous communication channels presented in the userinterface.
 26. The system of claim 17, wherein the list of candidateparticipants are identified from only a portion of the email that wasviewable upon the detecting.
 27. A computer program product comprising:a computer readable storage medium having program code stored thereon,the program code, which when executed by a computer hardware systemassociated with a user, causes the computer hardware system to perform:detecting the user donning a wearable peripheral device communicativelylinked with the computer hardware system; retrieving, based upon thedetecting, an email currently being displayed by an email applicationexecuting within the computer hardware system; displaying, within a userinterface separate from the email application, a list of candidateparticipants identified from the email; and sending, to at least one ofthe candidate participants selected from within the user interface, aninvite for a synchronous communication session.
 28. The computer programproduct of claim 27, wherein the retrieving is performed by a contextagent executing within the computer hardware system and separate fromthe email application.
 29. The computer program product of claim 28,wherein the context agent is configured to communicate with the emailapplication and receive the email.
 30. The computer program product ofclaim 28, wherein the context agent is configured to identify anavailability of each of the candidate participants.
 31. The computerprogram product of claim 30, wherein an availability of a particularcandidate participant is displayed within the user interface.
 32. Thecomputer program product of claim 30, wherein the context agent isconfigured to select a particular type of synchronous communicationsession based upon availabilities of the candidate participants.
 33. Thecomputer program product of claim 27, wherein the detecting is basedupon a movement of the wearable peripheral device.
 34. The computerprogram product of claim 27, wherein the invite is sent only to eachcandidate participant selected within the user interface.
 35. Thecomputer program product of claim 27, wherein the user interfacepresents a plurality of different synchronous communication channels,and the synchronous communication session is conducted over asynchronous communication channel selected from the plurality ofdifferent synchronous communication channels presented in the userinterface.
 36. The computer program product of claim 27, wherein thelist of candidate participants are identified from only a portion of theemail that was viewable upon the detecting.